There is no vdb.xml file or vdb artifact of any kind for deployment in embedded. Models (schemas) are deployed as a set to form a named vdb.

• There is no direct vdb versioning concept in embedded.

There is no JDBC/ODBC socket transport in embedded. You are expected to obtain a Driver connection via the EmbeddedServer.getDriver method.

• A javax.sql.DataSource is not provided for embedded. The embedded server is by default able to detect thread bound transactions and appropriately propagate the transaction to threads launched as part of request processing. Transaction processing requires setting the TransactionManager in the EmbeddedConfiguration used to start the EmbeddedServer.

Translators instances can be scoped to a VDB in AS using declarations in a vdb.xml file, however named instances are scoped to the entire EmbeddedServer and must be registered via the EmbeddedServer.addTranslator method.

A MetadataRepository is scoped to a VDB in AS, but is scoped to the entire EmbeddedServer instance and must be registered via the EmbeddedServer.addMetadataRepository method.